Remote access to mediated content connection and control

ABSTRACT

A controlled content system for providing a controlled and contained environment that is remotely accessible is disclosed. An application on the end user device is modified to allow certain sites and services to be mediated in a mid-link server. The app uses policies to know when to access the mid-link server for the controlled and contained environment. Policies can specify the type of processing performed on the mid-link server. Some embodiments support the app selectively using the mid-link server for mediated sites and services. A client spoofer at the mid-link server spoofs direct interaction with the certain sites and the services as if the end user device was directly interacting with the plurality of remote services.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 17/028,696 entitled “CLIENT SOFTWARE CONNECTION INSPECTION AND ACCESS CONTROL,” filed on Sep. 22, 2020, the contents of which is incorporated by reference in its entirety for all purposes.

BACKGROUND

This disclosure relates in general to remote access to networks with security and, but not by way of limitation, to remote access to a mediated content connection amongst other things.

The modern trend is to have a distributed work force or even have employees work at home. Within the enterprise, security is easier to enforce with everyone being co-located on the same local area network (LAN). As employees connect to services and sites from outside the LAN, security and control is more difficult to maintain.

There are reasons for employees to access certain web sites. However, there may be certain interaction with those sites that is not appropriate. For example, someone in marketing may need to post a video with information on company products, but commenting on that video may not be appropriate. Mediating web sites is difficult to do with user owned devices such as cell phones and tablets.

There is technology to redirect users to filtered or mediated versions a web site. Although providing a certain level of corporate control, it is awkward to see redirected URLs in a browser for example. Where there is a local application that provides this filtration or mediation, users can disable the application to avoid the filtration or modification of inappropriate interaction.

SUMMARY

In one embodiment, the present disclosure provides a controlled and contained environment that is remotely accessible. A controlled content system for providing a controlled and contained environment that is remotely accessible is disclosed. An application on the end user device is modified to allow certain sites and services to be mediated in a mid-link server. The app uses policies to know when to access the mid-link server for the controlled and contained environment. Policies can specify the type of processing performed on the mid-link server. Some embodiments support the app selectively using the mid-link server for mediated sites and services. A client spoofer at the mid-link server spoofs direct interaction with the certain sites and the services as if the end user device was directly interacting with the plurality of remote services.

In another embodiment, a controlled content system for providing policy-controlled communication over the Internet between a plurality of remote services and an application executing on a client device is disclosed. The controlled content system includes the application and a mid-link server. The application is configured to execute on the client device. The application includes a first policy component, a client endpoint, and an interceptor component. The first policy component has a first plurality of policies for network packet traffic for the application. The first plurality of policies specify one or more aspects of processing of network sessions from the application to the plurality of remote services. The client endpoint is coupled to a digitally protected tunnel. The interceptor component identifies the network packet traffic according to the first plurality of policies. The network packet traffic is diverted to the client endpoint for transport over the digitally protected tunnel. An Hypertext Transfer Protocol (HTTP) stack for connection with remote services based on the network packet traffic identified by the first plurality of policies as mediated targets. A wrapper to identify a call to the HTTP stack, the call is to a remote service that has applicable policies for mediation. A mediated program that applies a set of policies on the network packet traffic. The set of policies include the first plurality of policies and a second plurality of policies. A mid-link server is coupled to the digitally protected tunnel, and includes a mid-link endpoint, a second policy component, a router component, and an inspection component. The mid-link endpoint that terminates the digitally protected tunnel. The second policy component uses the second plurality of policies to specify at least: policy-based routing, packet re-addressing, and content mediation rules on the network packet traffic identified by the first plurality of policies. The network packet traffic arriving from the digitally protected tunnel. The router component is interposed between the digitally protected tunnel and the plurality of remote services. The router component operates to route network packet traffic between the digitally protected tunnel and the plurality of remote services via a route specified by the second plurality of policies. The inspection component analyzes network packet traffic in accordance with the second plurality of policies. A client spoofer that spoofs direct interaction with the plurality of remote services as if the client device was directly interacting with the plurality of remote services. The interaction is portrayed on the mediated program as if it were performed by the client device alone. The plurality of remote services presumes direct interaction with the client device. The application operates with the plurality of remote services to provide functionality to the client device.

In yet embodiment, a method for providing policy-controlled communication over the Internet between a plurality of remote services and an application executing on a client device is disclosed. The application is configured to execute on the client device. The application is comprised of a first policy component, a client endpoint, a mediated program, an Hypertext Transfer Protocol (HTTP) stack, and an interceptor component. One or more aspects of processing of network sessions from the application to the plurality of remote services according to a first plurality of policies are specified for the network packet traffic for the first policy component of the application. The first plurality of policies are used to identify packet traffic with an interceptor component. A wrapper identifies a call to the HTTP stack. The call is to a remote service that has applicable policies for mediation. The HTTP stack is used for connecting with remote services based on the network packet traffic identified by the first plurality of policies as mediated targets. The network packet traffic is diverted to the client endpoint for transport over a digitally protected tunnel. The mid-link server is coupled to the digitally protected tunnel. The mid-link server includes a mid-link endpoint, a second policy component, a router component, an inspection component, and a client spoofer. The digitally protected tunnel is terminated with the mid-link endpoint. The second policy component according to a second plurality of policies specifies at least: policy-based routing, packet re-addressing, and content mediation rules on the network packet traffic identified by the first plurality of policies. The network packet traffic arriving from the digitally protected tunnel. The router component interposed between the digitally protected tunnel and the plurality of remote services routes network packet traffic between the digitally protected tunnel and the plurality of remote services via a route specified by the second plurality of policies. The inspection component in accordance with the second plurality of policies analyzes the network packet traffic. The application operates with the plurality of remote services to provide functionality to the client device.

In still another embodiment, a controlled content system for providing policy-controlled communication over the Internet between a plurality of remote services and an application executing on a client device is disclosed. The controlled content system comprising a plurality of processors and memories with code for: configuring the application to execute on the client device, wherein the application comprises a first policy component, a client endpoint, a mediated program, an Hypertext Transfer Protocol (HTTP) stack, and an interceptor component; specifying one or more aspects of processing of network sessions from the application to the plurality of remote services according to a first plurality of policies for network packet traffic for the first policy component of the application; identifying with an interceptor component packet traffic according to the first plurality of policies, wherein the network packet traffic is diverted to the client endpoint for transport over a digitally protected tunnel; identifying by a wrapper a call to the HTTP stack, the call is to a remote service that has applicable policies for mediation, wherein the HTTP stack is used for connecting with remote services based on the network packet traffic identified by the first plurality of policies as mediated targets; coupling a mid-link server to the digitally protected tunnel, wherein the mid-link server comprises a mid-link endpoint, a second policy component, a router component, and an inspection component and a client spoofer; terminating the digitally protected tunnel with the mid-link endpoint; specifying at least: policy-based routing, packet re-addressing, and content mediation rules on the network packet traffic identified by the first plurality of policies. The network packet traffic arriving from the digitally protected tunnel, with the second policy component according to a second plurality of policies; applying by the mediated program of the application, the first plurality of policies and the second plurality of policies on the network packet traffic; routing, with the router component interposed between the digitally protected tunnel and the plurality of remote services, the network packet traffic between the digitally protected tunnel and the plurality of remote services via a route specified by the second plurality of policies; spoofing by the client spoofer, direct interaction with the plurality of remote services as if the client device was directly interacting with the plurality of remote services, wherein: the interaction is portrayed on the mediated program as if it were performed by the client device alone, and the plurality of remote services presumes direct interaction with the client device; and analyzing the network packet traffic with the inspection component in accordance with the second plurality of policies, wherein the application operates with the plurality of remote services to provide functionality to the client device

Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating various embodiments, are intended for purposes of illustration only and are not intended to necessarily limit the scope of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is described in conjunction with the appended figures:

FIG. 1 depicts a block diagram of an embodiment of a controlled content system;

FIGS. 2A-2C depict block diagrams of embodiments of an end user device;

FIGS. 3A-3E depict block diagrams of embodiments of a mediated app;

FIG. 4 depicts a block diagram of an embodiment of an access resource server (ARS);

FIG. 5 illustrates a flowchart of an embodiment of a process for converting apps to supporting mediation; and

FIGS. 6A-6D illustrate flowcharts of embodiments of a process for processing mediated content with an app.

In the appended figures, similar components and/or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.

DETAILED DESCRIPTION

The ensuing description provides preferred exemplary embodiment(s) only, and is not intended to limit the scope, applicability or configuration of the disclosure. Rather, the ensuing description of the preferred exemplary embodiment(s) will provide those skilled in the art with an enabling description for implementing a preferred exemplary embodiment. It is understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope as set forth in the appended claims.

Referring first to FIG. 1 a block diagram of an embodiment of a controlled content system 100 is shown that mediates computing activity of end users 112. End user device(s) 116 such as phones, tablets, PCs, IoT devices, and any other network connected devices that run third party apps can be mediated to using an access resource server (ARS) to control and contain the environment for mediated apps. The third party apps are applications running on the operating system of the end user devices 116. A policy store 115 holds policies for each end user device 116 with a mediated app and each access resource server 108.

The mediated apps and other third party apps use content and processing from content sites 104 (e.g., web sites, streaming content, etc.) and services 120 (e.g., SaaS tools, databases, cloud service providers, etc.). The mediated apps could be any software that runs on the operating system of the end user device (e.g., browser, driver, utility, application, etc.). Mediated apps receive direction from the policy store 115 such as who can use them, what sites and services can they communicate with, what network traffic is routed to the ARS, prohibited network traffic, etc.

Locating content sites 104 and services 120 on the Internet uses domain name services (DNS) 168. The DNS 168 provides IP addresses in response to providing a domain name, for example, a query for acme.com is returned as the 226.204.110.960 IP address. That allows various software on the end user device 116 to find content sites 104 and services 120. DNS acts recursively to pass requests closer to the requesting end user device 116 until an authoritative DNS is found. In this process, traffic and loading can be managed to edge servers that are preferred by the content sites 104 and services 120.

The ARS 108 is also called a mid-link server meaning that for mediated connections, the ARS 108 sits as a “man-in-the-middle” intentionally to mediate some or all content sites 104 and services. Mediated apps direct certain traffic to the ARS 108 for a policy-controlled environment using the policy store 115. For example, content sites 104 can have certain features disabled, filtered or modified by the ARS 108 so that the mediated app behaves differently than if it were to directly connect to the content site 104. Some embodiments have policies that selectively direct traffic to the ARS 108 based upon whether it is done during work hours or not or using a work account or not. For example, in the evenings using a personal Youtube™ account, the end user 112 may have unfettered access with the ability to leave comments on a video. During work hours and/or using a work account, the same end user 112 would be prevented from leaving comments at that same content site 104.

With reference to FIG. 2A-2C, block diagrams of embodiments of an end user device 116 are shown. Mediated apps 216 have varying local and remote control using different mechanisms in the different embodiments. A policy cache 220 holds the subset of policies from the policy store 115 that are intended for the end user device 116. Some embodiments could forgo a policy cache 220 altogether and query a remote policy store 115 as needed in real time.

A local area network (LAN) serves the physical location of the end user device(s) 116 even though that may be temporary and connects to the Internet using a gateway and/or router typically. Some policies from the policy cache 220 may be specific to a particular LAN 222, location, work hours, or other criteria. For example, use of USB drives may be prohibited while connected to the LAN directly or through a VPN to avoid possible theft of trade secrets.

The end user device 116 has a browser 226 and apps 232 that are unmodified programs 250 which are not directly mediated through modification of their code. Some enterprises may not allow download or install of some of these unmodified programs 250 that lack mediation for security and other reasons. A mediated browser 218 and mediated apps 216 are mediated programs 254 installed on the end user device 116 that use the ARS 108 and apply local and/or mid-link policies upon digital packet data traveling within the LAN or externally to the Internet. Some mediated programs 254 are designed with this functionality while others are modified either at compilation and/or run time to allow policy control.

Referring specifically to FIG. 2A, this embodiment of an end user device 116-1 uses a client 210 to assist mediated programs 254 and apply policy control to unmodified programs 250. The client 210 has a DNS 208 that is authoritative for certain unmodified programs 250. The DNS 208 may be part of the operating system in some embodiments. When a unmodified program 250 requests a connection with a content site 104 or service 120 for which there is a policy specifying mediation, the DNS 208 returns an address for the ARS 108 to fulfill the requested interaction. In this way, unmodified programs 250 can be mediated.

The client 210 can apply policies 220 to the end user device 116 in addition to mediating unmodified programs 250. For example, there may be a policy that: requires a recent anti-virus scan prior to allowing connection to the LAN 222, doesn't allow certain programs to be installed, prevents emails to certain address(es), etc.

This embodiment includes an endpoint tunnel 215 in the client 210. The endpoint tunnel 215 digitally separates packet traffic between the end user device 116 and the ARS 108. There may be a number of endpoint tunnels 215 in operation simultaneously for different for different functions or programs 250, 254. A virtual private network (VPN) connection, HTTPS connection (e.g., HTTP 1.0, HTTP 2.0, HTTP 3.0), and/or public or private key encryption can be used for the endpoint tunnel 215 for different connections.

With reference to the embodiment of FIG. 2B, an end user device 116-2 is shown that does not include the client 210 of the embodiment of FIG. 2A. Back to the FIG. 2B embodiment, each of the mediated programs 254 include one or more endpoint tunnels 215 that connect with the ARS 108. The mediated programs 254 also have code to understand policies from the policy cache 220.

Referring next to FIG. 2C, an end user device 116-3 includes mediated programs 254 that have integral policy caches 220. Each policy cache 220 gathers the relevant policies from the policy store 115 Instead of using an endpoint tunnel 215, HTTPS is used to connect the mediated programs 254 to the ARS 108. Some operating systems have HTTPS built directly into them or the code could be included in the mediated program 254. Other embodiments, could use a VPN function in the operating system or built-in for the endpoint tunnel 215 to convey traffic to the ARS 108.

With reference to FIGS. 3A-3E, block diagrams of embodiments of a mediated program 254 are shown. Different mediated programs 254 have different functions and a number of embodiments are detailed in these figures. Generally, there are app functions 318 to implement the various features of the mediated program 254. Typically, there is an interface 104 of some sort to allow end user 112 interaction with the mediated program. A network interface 324 allows communication with the LAN 222 and Internet when so connected.

Referring specifically to FIG. 3A, a mediated program 254-1 is shown that uses a HTTP stack 208 to connect to the ARS 108 for mediated targets. A look-up table or the like indicates when a particular target is mediated or not. For the targets that are not mediated, communication is direct using the HTTP stack 308. The app functions 318 could use the ARS 108 for some communication and not for other communication.

With reference to FIG. 3B, a mediated program 254-2 is shown that includes a mediation switch 314. Mediated targets are directed by the mediation switch 314 to go through the ARS 108 using the tunnel endpoint 215, while the remainder communicate with their target using the HTTP stack 308 without use of the ARS 108. A list of mediated content sites 104 and services 120 is maintained by the app functions and gathered from the policy store 115.

Referring next to FIG. 3C, a mediated program 254-3 is shown that has the mediation switch 314 determine what goes to the ARS 108 using the policy cache 220. The mediation switch can have sophisticated algorithms that determines which traffic is mediated through the ARS 108, for example, time of day, location of the end user device 116, security status of the end user device 116, stability status of the mediated program 254, speed and/or latency of the mediated connection, etc.

With reference specifically to FIG. 3D, a mediated program 254-4 is shown that determines which traffic goes to the ARS 108 in a mediated HTTP stack 328. The policy cache 220 provides guidance to the mediated HTTP stack 328 so the ARS can be utilized or not. The tunnel endpoint 215 uses HTTPS when communication is with a mediated target. The mediated HTTP stack 328 can use the same API calls as popular open source or proprietary HTTP stacks so that merely switching out that library or those libraries along with adding a policy cache 220 makes existing software capable of leveraging the ARS 108. In some cases, open source versions of software can be converted with little more than substitution and recompiling.

Referring next to FIG. 3E, a mediated program 254-5 is shown that sends all network communication through the tunnel endpoint 215 to the ARS 108. The ARS 108 can decide if a particular target needs mediation or not. The tunnel endpoint 215 could use HTTP or a VPN to connect with the ARS 108.

Although the various embodiments of FIGS. 3A-3E have predetermined policies for determining what are mediated targets and the policies to apply, other embodiments could use machine learning to make these determinations. Certain requests for a HTTPS session, for example, might be intercepted and replaced with tunnel endpoint 215 transport to the ARS 108. Observation of what calls result in a HTTP session to which IP addresses could be observed over time to allow intelligent re-routing. The app developer may not cooperate in producing a mediated version of their app 232 and the learning algorithm could intelligently reroute even though not knowing the syntax of an API call initially. That learning could be shared with other instances of the same app 232 to allow diverting more and more traffic over time to the ARS 108 for a policy controlled connection.

With reference to FIG. 4, a block diagram of an embodiment of an access resource server (ARS) 108 is shown, which is located mid-link in a mediated connection. Different variations of the ARS 108 are described in more detail in U.S. application Ser. No. 16/602,698, filed No. 20, 2019, entitled, ZERO TRUST AND ZERO KNOWLEDGE APPLICATION ACCESS SYSTEM, which is hereby incorporated by reference for all purposes. Generally, the ARS 108 spoofs direct interaction with targets as if the end user device 116 was directly interacting. Content sites 104 and services 120 (i.e., targets) generally presume direct interaction with end user devices 116. IP addresses and other information from end user devices 116 are used by targets to localize content, authenticate, or otherwise customize the end user 112 experience.

Tunnel endpoints 215 connect with mediated programs 254 or unmodified programs 250 redirected to the ARS 208. The tunnel endpoints 215 support a number of protocols in various embodiments including HTTP, HTTPS, VPN, and/or encryption. Once the digital packet data is outside the tunnel, it passes through a gateway 404 and to a packet inspector 408. If in plain text, the packet inspector can perform various analysis on the digital packet data to check for nefarious traffic according to the policies 412 gathered from the policy store 115. Each program 250, 254, enterprise, end user device 116 and/or end user 112 may have different policies assigned to its traffic.

Content mediation 416 is also performed according to the relevant policies 412. Mediation may include blocking inappropriate web sites, photos or other content. Portions or features of web sites can be blocked, for example, the ability to post comments. Content mediation 416 can happen in both directions preventing content from being posted to a target, for example. Entire web sites can be rewritten as part of the content mediation to limit functionality and/or access to certain data.

Client spoofers 424 act as though they are the end user device 116 that is directly connecting with a target. The target may use HTTP, HTTPS, VPN, or encrypted connections to the client spoofers 424. Any digital packet from the target can also have content mediation 416 and packet inspection 408 before returning by way of the tunnel endpoints 215. A router 412 connects the ARS to the Internet and ultimately the targets.

Referring next to FIG. 5, a flowchart of an embodiment of a conversion process 500 for reformulating apps to supporting mediation is shown. Many applications are available in open source form so that this process might convert them to be compatible with the ARS 108 to mediate content. Third party app developers might use this process to add this compatibility too. Without cooperation, a third party app can be compiled with wrapper or shim code that supports the mediation process for controlled targets. Any app with or without cooperation can potentially be recompiled with the wrapper or shim code to support the mediation process.

The depicted portion of the process begins in block 504 where the source code for the app or program is loaded. Depending on the design of the code, the HTTP stack 308 is manually or automatically identified. The HTTP stack 308 can be modified to support the ARS 108 or replaced with a mediated HTTP stack 328. In block 512, other modules or functions can be added to the source code, for example, a mediated switch, policy cache or call to one, a tunnel endpoint, or any of the other blocks shown in FIGS. 3A-3F. Different API connections between modules are rewritten in block 516 to reroute some calls to mediate traffic with targets.

In block 520, the modified code is compiled into a mediated program 254. Testing is performed in block 524. Where there problems, processing looks back to block 516. Otherwise, the mediated program 254 is ready for use. In this way, most unmodified programs 250 can be rewritten into a mediated program 250.

With reference to FIGS. 6A-6C, flowcharts of embodiments of a mediation process 600 for local redirection of mediated interaction with an program 254 are shown. The various embodiments discussed above follow different processes to achieve a controlled and contained environment on the ARS 108 through remote access from the end user device 116.

Referring specifically to FIG. 6A, a flowchart of an embodiment of a mediation process 600-1 is shown. This embodiment uses a wrapper or shim of code that learns over time how to mediate more calls to targets. The unmodified program 250 remains largely unchanged in this embodiment. A machine learning algorithm can make guesses based upon past outcomes to become more accurate over time. The depicted portion of the process beings in block 604, where a call to the HTTP stack 308 is observed by the wrapper. In block 608, the resulting traffic generated from the call is observed, for example, handshaking and IP address.

It is determined in block 612 that the call is to a target that has applicable policies for mediation. Future calls that are similar are intercepted in block 616 and directed to the ARS 108 for fulfillment and other processing specified by the policies in block 620. The ARS 108 spoofs interaction with the mediated target on behalf of the end user device 116. Once an intercepted call is successfully handled once or a number of times, the table of calls to the HTTP stack 308 to intercept is updated in block 628. Those calls in the table are intercepted in the future to go to the ARS 108 rather than the mediated target directly.

With specific reference to FIG. 6B, a flowchart of an embodiment of a mediation process 600-2 is shown. In this embodiment, a mediation switch 314 is used to pass uncontrolled traffic and process mediated traffic through the ARS 108. The depicted portion of the process begins in block 602 where the mediated program 254 formulates a HTTP call after analysis of the relevant policies. For a target that is not subject to mediation as indicted in a policy in block 606, processing continues to block 610 where the HTTP connection between the end user device 116 and the target is configured without the ARS 108 in the middle.

Should the HTTP call be determined in block 606 to be to a mediated target, processing diverts to block 608 where additional policy restrictions are determined for the mediated target and/or other conditions that the policy might depend upon. In block 610, a tunnel endpoint 215 is configured to connect to the ARS 108, for example, a HTTPS or VPN connection. Then processing continues to blocks 620, 624 and 632 in a fashion similar to the embodiment of FIG. 6A.

Referring specifically to FIG. 6C, a flowchart of an embodiment of a mediation process 600-3 is shown. This embodiment applies policy restrictions at the ARS 108 or at least some of them. The handling of connections to targets not being mediated is the same as the embodiment of FIG. 6B. For a mediated target as determined in block 606, processing goes to block 610 where the tunnel to the ARS 108 is configured. In block 620, the calls directed to the ARS are fulfilled and otherwise processed. Any policy restrictions are determined for the mediated target in block 608. Processing continues to blocks 624 and 632 like the prior two embodiments.

With specific reference to FIG. 6D, a flowchart of an embodiment of a mediation process 600-4 is shown. In this embodiment, all traffic is sent to the ARS 108 for handling. This is true even for an unmediated target. Once the HTTP call is formulated in block 602, the tunnel to the ARS 108 is configured in block 610 to direct all calls to the ARS 108 for processing. Any further policy restrictions are applied in block 608. The ARS 108 spoofs interaction with the mediated target in block 624. Finally, the call is fulfilled by the ARS 108 in block 632. The interaction is portrayed on the mediated program 254 as if it were performed by the end user device 116 alone.

A number of variations and modifications of the disclosed embodiments can also be used. For example, the above embodiments modify code to create a mediated program 254, other embodiments could modify the HTTP stack and/or VPN functionality in the operating system. Policy controlled traffic could be diverted by the operating system to the ARS 108.

Specific details are given in the above description to provide a thorough understanding of the embodiments. However, it is understood that the embodiments may be practiced without these specific details. For example, circuits may be shown in block diagrams in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

Implementation of the techniques, blocks, steps and means described above may be done in various ways. For example, these techniques, blocks, steps and means may be implemented in hardware, software, or a combination thereof. For a hardware implementation, the processing units may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described above, and/or a combination thereof

Also, it is noted that the embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a swim diagram, a data flow diagram, a structure diagram, or a block diagram. Although a depiction may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but could have additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination corresponds to a return of the function to the calling function or the main function.

Furthermore, embodiments may be implemented by hardware, software, scripting languages, firmware, middleware, microcode, hardware description languages, and/or any combination thereof. When implemented in software, firmware, middleware, scripting language, and/or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine readable medium such as a storage medium. A code segment or machine-executable instruction may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a script, a class, or any combination of instructions, data structures, and/or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, and/or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

For a firmware and/or software implementation, the methodologies may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. Any machine-readable medium tangibly embodying instructions may be used in implementing the methodologies described herein. For example, software codes may be stored in a memory. Memory may be implemented within the processor or external to the processor. As used herein the term “memory” refers to any type of long term, short term, volatile, nonvolatile, or other storage medium and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.

Moreover, as disclosed herein, the term “storage medium” may represent one or more memories for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other machine readable mediums for storing information. The term “machine-readable medium” includes, but is not limited to portable or fixed storage devices, optical storage devices, and/or various other storage mediums capable of storing that contain or carry instruction(s) and/or data.

While the principles of the disclosure have been described above in connection with specific apparatuses and methods, it is to be clearly understood that this description is made only by way of example and not as limitation on the scope of the disclosure. 

What is claimed is:
 1. A controlled content system for providing policy-controlled communication over the Internet between a plurality of remote services and an application executing on a client device, the controlled content system comprising: the application configured to execute on the client device, the application comprising: a first policy component with a first plurality of policies for network packet traffic for the application, wherein the first plurality of policies specify one or more aspects of processing of network sessions from the application to the plurality of remote services, a client endpoint coupled to a digitally protected tunnel, and an interceptor component that identifies the network packet traffic according to the first plurality of policies, wherein the network packet traffic is diverted to the client endpoint for transport over the digitally protected tunnel, an Hypertext Transfer Protocol (HTTP) stack for connection with remote services based on the network packet traffic identified by the first plurality of policies as mediated targets, a wrapper to identify a call to the HTTP stack, the call is to a remote service that has applicable policies for mediation, and a mediated program that applies a set of policies on the network packet traffic, wherein the set of policies include the first plurality of policies and a second plurality of policies; and a mid-link server, coupled to the digitally protected tunnel, the mid-link server comprising: a mid-link endpoint that terminates the digitally protected tunnel, a second policy component, wherein: the second policy component uses the second plurality of policies to specify at least: policy-based routing, packet re-addressing, and content mediation rules on the network packet traffic identified by the first plurality of policies, the network packet traffic arriving from the digitally protected tunnel, and a router component interposed between the digitally protected tunnel and the plurality of remote services, wherein the router component operating to route the network packet traffic between the digitally protected tunnel and the plurality of remote services via a route specified by the second plurality of policies, a client spoofer that spoofs direct interaction with the plurality of remote services as if the client device was directly interacting with the plurality of remote services, wherein: the interaction is portrayed on the mediated program as if it were performed by the client device alone, and the plurality of remote services presumes direct interaction with the client device, and an inspection component that analyzes the network packet traffic in accordance with the second plurality of policies, wherein the application operates with the plurality of remote services to provide functionality to the client device.
 2. The controlled content system for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 1, wherein the digitally protected tunnel is a Virtual Private Network (VPN).
 3. The controlled content system for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 1, wherein the digitally protected tunnel is one of a Hypertext Transfer Protocol Secure (HTTPS) or Hypertext Transfer Protocol (HTTP) session.
 4. The controlled content system for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 1, wherein the application is a web browser, and the plurality of remote services are a plurality of web sites.
 5. The controlled content system for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 1, wherein the mid-link server further comprises a mediation component that performs content mediation based on the second plurality of policies.
 6. The controlled content system for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 1, wherein the interceptor component allows the network packet traffic not identified by the first plurality of policies to use the HTTP stack to directly communicate with the plurality of remote services avoiding the mid-link server.
 7. The controlled content system for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 1, wherein the plurality of remote services comprises a plurality of web sites.
 8. The controlled content system for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 1, wherein Internet Protocol (IP) address from the client device is used by the plurality of remote services to localize content, authenticate, or customize user experience at the client device.
 9. A method for providing policy-controlled communication over the Internet between a plurality of remote services and an application executing on a client device, the method comprising: configuring the application to execute on the client device, wherein the application comprises a first policy component, a client endpoint, a mediated program, an Hypertext Transfer Protocol (HTTP) stack, and an interceptor component; specifying one or more aspects of processing of network sessions from the application to the plurality of remote services according to a first plurality of policies for network packet traffic for the first policy component of the application; identifying with an interceptor component the network packet traffic according to the first plurality of policies, wherein the network packet traffic is diverted to the client endpoint for transport over a digitally protected tunnel; identifying by a wrapper a call to the HTTP stack, the call is to a remote service that has applicable policies for mediation, wherein the HTTP stack is used for connecting with remote services based on the network packet traffic identified by the first plurality of policies as mediated targets; coupling a mid-link server to the digitally protected tunnel, wherein the mid-link server comprises a mid-link endpoint, a second policy component, a router component, an inspection component, and a client spoofer; terminating the digitally protected tunnel with the mid-link endpoint; specifying at least: policy-based routing, packet re-addressing, and content mediation rules on the network packet traffic identified by the first plurality of policies, the network packet traffic arriving from the digitally protected tunnel, with the second policy component according to a second plurality of policies; applying by the mediated program of the application, the first plurality of policies and the second plurality of policies on the network packet traffic; routing, with the router component interposed between the digitally protected tunnel and the plurality of remote services, the network packet traffic between the digitally protected tunnel and the plurality of remote services via a route specified by the second plurality of policies; spoofing by the client spoofer, direct interaction with the plurality of remote services as if the client device was directly interacting with the plurality of remote services, wherein: the interaction is portrayed on the mediated program as if it were performed by the client device alone, and the plurality of remote services presumes direct interaction with the client device; and analyzing the network packet traffic with the inspection component in accordance with the second plurality of policies, wherein the application operates with the plurality of remote services to provide functionality to the client device.
 10. The method for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 9, wherein the digitally protected tunnel is a Virtual Private Network (VPN).
 11. The method for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 9, wherein the digitally protected tunnel is one of a Hypertext Transfer Protocol Secure (HTTPS) or Hypertext Transfer Protocol (HTTP) session.
 12. The method for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 9, wherein the application is a web browser and the plurality of remote services are a plurality of web sites.
 13. The method for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 9, wherein the mid-link server further comprises a mediation component that performs content mediation based on the second plurality of policies.
 14. The method for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 9, wherein the interceptor component allows the network packet traffic not identified by the first plurality of policies to use the HTTP stack to directly communicate with the plurality of remote services avoiding the mid-link server.
 15. The method for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 9, wherein the plurality of remote services comprises a plurality of web sites.
 16. The method for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 9, wherein the application is developed by a third party.
 17. A controlled content system for providing policy-controlled communication over the Internet between a plurality of remote services and an application executing on a client device, the controlled content system comprising a plurality of processors and memories with code for: configuring the application to execute on the client device, wherein the application comprises a first policy component, a client endpoint, a mediated program, an Hypertext Transfer Protocol (HTTP) stack, and an interceptor component; specifying one or more aspects of processing of network sessions from the application to the plurality of remote services according to a first plurality of policies for network packet traffic for the first policy component of the application; identifying with an interceptor component packet traffic according to the first plurality of policies, wherein the network packet traffic is diverted to the client endpoint for transport over a digitally protected tunnel; identifying by a wrapper a call to the HTTP stack, the call is to a remote service that has applicable policies for mediation, wherein the HTTP stack is used for connecting with remote services based on the network packet traffic identified by the first plurality of policies as mediated targets; coupling a mid-link server to the digitally protected tunnel, wherein the mid-link server comprises a mid-link endpoint, a second policy component, a router component, an inspection component, and a client spoofer; terminating the digitally protected tunnel with the mid-link endpoint; specifying at least: policy-based routing, packet re-addressing, and content mediation rules on the network packet traffic arriving identified by the first plurality of policies, the network packet traffic arriving from the digitally protected tunnel, with the second policy component according to a second plurality of policies; applying by the mediated program of the application, the first plurality of policies and the second plurality of policies on the network packet traffic; routing, with the router component interposed between the digitally protected tunnel and the plurality of remote services, the network packet traffic between the digitally protected tunnel and the plurality of remote services via a route specified by the second plurality of policies; spoofing by the client spoofer, direct interaction with the plurality of remote services as if the client device was directly interacting with the plurality of remote services, wherein: the interaction is portrayed on the mediated program as if it were performed by the client device alone, and the plurality of remote services presumes direct interaction with the client device; and analyzing the network packet traffic with the inspection component in accordance with the second plurality of policies, wherein the application operates with the plurality of remote services to provide functionality to the client device.
 18. The controlled content system for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 17, wherein the digitally protected tunnel is a Virtual Private Network (VPN).
 19. The controlled content system for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 17, wherein the digitally protected tunnel is one of a Hypertext Transfer Protocol Secure (HTTPS) or Hypertext Transfer Protocol (HTTP) session.
 20. The controlled content system for providing policy-controlled communication over the Internet between the plurality of remote services and the application executing on the client device of claim 17, wherein the interceptor component allows the network packet traffic not identified by the first plurality of policies to use the HTTP stack to directly communicate with the plurality of remote services avoiding the mid-link server. 